Blockchain technique for agile software development framework

ABSTRACT

An example operation may include one or more of transmitting a copy of the master ledger when a developer joins a network, receiving proposed changes to the master ledger, and updating the master ledger at the branch hash.

TECHNICAL FIELD

This application generally relates to blockchain technology, and more particularly, to applying blockchain technique for agile software development framework.

BACKGROUND

A ledger is commonly defined as an account book of entry, in which transactions are recorded. A distributed ledger is ledger that is replicated in whole or in part to multiple computers. A Cryptographic Distributed Ledger (CDL) can have at least some of these properties: irreversibility (once a transaction is recorded, it cannot be reversed), accessibility (any party can access the CDL in whole or in part), chronological and time-stamped (all parties know when a transaction was added to the ledger), consensus based (a transaction is added only if it is approved, typically unanimously, by parties on the network), verifiability (all transactions can be cryptographically verified). A blockchain is an example of a CDL. While the description and figures herein are described in terms of a blockchain, the instant application applies equally to any CDL.

A distributed ledger is a continuously growing list of records that typically apply cryptographic techniques such as storing cryptographic hashes relating to other blocks. A blockchain is one common instance of a distributed ledger and may be used as a public ledger to store information. Although, primarily used for financial transactions, a blockchain can store various information related to goods and services (i.e., products, packages, status, etc.). A decentralized scheme provides authority and trust to a decentralized network and enables its nodes to continuously and sequentially record their transactions on a public “block”, creating a unique “chain” referred to as a blockchain. Cryptography, via hash codes, is used to secure an authentication of a transaction source and removes a central intermediary. A blockchain is a distributed database that maintains a continuously-growing list of records in a blockchain blocks, which are secured from tampering and revision due to their immutable properties. Each block contains a timestamp and a link to a previous block. A blockchain can be used to hold, track, transfer and verify information. Since a blockchain is a distributed system, before adding a transaction to the blockchain ledger, all peers need to reach a consensus status.

Agile development methodology is based on short sprints where work is done at high velocity continuously delivering features and releases daily. Waterfall methods are quite the opposite in that they result around long roadmaps planned months in advance where the work has a final end date, i.e., all the work being delivered as one large package. In heavily regulated industries, companies trust each other at a business level but often not at the engineering level. Due to fears around data manipulation, source code is often developed in silos and tossed over firewalls creating a linear, non-transparent, waterfall method of development ruled by regulation.

In these environments, vertical integration is often too expensive, where contractors come to collaborate to build solutions for governments, banks, militaries, cities, etc. This process is very rigid for collaborative development. IBM™ is often one of these participants such as in the Defense sector. The technology described to solve this problem would today be considered a form of RegTech™.

In the current model, a user may use a private key and copyright statement to sign the copy guaranteeing the authenticity of the package from one vendor. However, this vendor still has the capability to alter the history prior to signing the newer package. What is needed is the ability to to establish additional processes to validate each change. With the proposed solution, the immutability of a blockchain can easily prevent such actions. For example, some embodiments may solve the problem of source code assets and records being altered when the source code assets and records move amongst different companies building solutions through partnerships in heavily regulated industries. This solution allows for a transparent social coding construct where regulatory approvals can be served through the smart contracts within the embodiments described in below.

SUMMARY

One example embodiment may provide a method that includes one or more of transmitting a copy of the master ledger when a developer joins a network. The method also includes receiving proposed changes to the master ledger and updating the master ledger at the branch hash.

Another example embodiment may provide a system that includes one or more a server configured to transmit a copy of the master ledger when a developer joins a network. The server is further configured to receive proposed changes to the master ledger and update the master ledger at the branch hash.

A further example embodiment may provide a non-transitory computer readable medium comprising instructions, that when read by a processor, cause the processor to perform one or more of transmit a copy of the master ledger when a developer joins a network. The processor is further configured to receive proposed changes to the master ledger and update the master ledger at the branch hash.

One example embodiment may provide a method that includes one or more transmitting a copy of the master ledger, wherein the master ledger comprises a code and history, receiving one or more changes to the copy of the master ledger, updating the master ledger when a required smart contract code standard is met, and initiating a push of the updated master ledger to one or more developer branches, enforcing synchronization across the one or more developer branches.

Another example embodiment may provide a system that includes one or more of transmit a copy of the master ledger, wherein the master ledger comprises a code and history, receive one or more changes to the copy of the master ledger, update the master ledger when a required smart contract code standard is met, and initiate a push of the updated master ledger to one or more developer branches to enforce synchronization across the one or more developer branches.

A further example embodiment may provide a non-transitory computer readable medium comprising instructions, that when read by processor, cause the processor to perform one or more of transmit a copy of the master ledger, wherein the master ledger comprises a code and history, receive one or more changes to the copy of the master ledger, update the master ledger when a required smart contract code standard is met, and initiate a push of the updated master ledger to one or more developer branches, enforcing synchronization across the one or more developer branches.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a network diagram with a blockchain, according to example embodiments.

FIG. 2A illustrates an example peer node blockchain architecture configuration for an asset sharing scenario, according to example embodiments.

FIG. 2B illustrates an example peer node blockchain configuration, according to example embodiments.

FIG. 3 is a diagram illustrating a permissioned blockchain network, according to example embodiments.

FIG. 4 illustrates a system messaging diagram for applying blockchain technique for agile software development framework, according to example embodiments.

FIG. 5A illustrates a flow diagram of an example method of applying blockchain technique for agile software development framework, according to example embodiments.

FIG. 5B illustrates another flow diagram of an example method of applying blockchain technique for agile software development framework, according to example embodiments.

FIG. 6A illustrates an example physical infrastructure configured to perform various operations on the blockchain in accordance with one or more operations described herein, according to example embodiments.

FIG. 6B illustrates an example smart contract configuration among contracting parties and a mediating server configured to enforce smart contract terms on a blockchain, according to example embodiments.

FIG. 7 illustrates an example computer system configured to support one or more of the example embodiments.

DETAILED DESCRIPTION

It will be readily understood that the instant components, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of at least one of a method, apparatus, non-transitory computer readable medium and system, as represented in the attached figures, is not intended to limit the scope of the application as claimed but is merely representative of selected embodiments.

The instant features, structures, or characteristics as described throughout this specification may be combined in any suitable manner in one or more embodiments. For example, the usage of the phrases “example embodiments”, “some embodiments”, or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment. Thus, appearances of the phrases “example embodiments”, “in some embodiments”, “in other embodiments”, or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

In addition, while the term “message” may have been used in the description of embodiments, the application may be applied to many types of network data, such as, packet, frame, datagram, etc. The term “message” also includes packet, frame, datagram, and any equivalents thereof. Furthermore, while certain types of messages and signaling may be depicted in exemplary embodiments they are not limited to a certain type of message, and the application is not limited to a certain type of signaling.

Example embodiments provide methods, devices, networks and/or systems, which provide an agile software development framework for blockchain.

A blockchain is a distributed system which includes multiple nodes that communicate with each other. A blockchain operates programs called chaincode (e.g., smart contracts, etc.), holds state and ledger data, and executes transactions. Some transactions are operations invoked on the chaincode. In general, blockchain transactions typically must be “endorsed” by certain blockchain members and only endorsed transactions may be committed to the blockchain and have an effect on the state of the blockchain. Other transactions which are not endorsed are disregarded. There may exist one or more special chaincodes for management functions and parameters, collectively called system chaincodes.

Nodes are the communication entities of the blockchain system. A “node” may perform a logical function in the sense that multiple nodes of different types can run on the same physical server. Nodes are grouped in trust domains and are associated with logical entities that control them in various ways. Nodes may include different types, such as a client or submitting-client node which submits a transaction-invocation to an endorser (e.g., peer), and broadcasts transaction-proposals to an ordering service (e.g., ordering node). Another type of node is a peer node which can receive client submitted transactions, commit the transactions and maintain a state and a copy of the ledger of blockchain transactions. Peers can also have the role of an endorser, although it is not a requirement. An ordering-service-node or orderer is a node running the communication service for all nodes, and which implements a delivery guarantee, such as a broadcast to each of the peer nodes in the system when committing transactions and modifying a world state of the blockchain, which is another name for the initial blockchain transaction which normally includes control and setup information.

A ledger is a sequenced, tamper-resistant record of all state transitions of a blockchain. State transitions may result from chaincode invocations (i.e., transactions) submitted by participating parties (e.g., client nodes, ordering nodes, endorser nodes, peer nodes, etc.). A transaction may result in a set of asset key-value pairs being committed to the ledger as one or more operands, such as creates, updates, deletes, and the like. The ledger includes a blockchain (also referred to as a chain) which is used to store an immutable, sequenced record in blocks. The ledger also includes a state database which maintains a current state of the blockchain. There is typically one ledger per channel. Each peer node maintains a copy of the ledger for each channel of which they are a member.

A chain is a transaction log which is structured as hash-linked blocks, and each block contains a sequence of N transactions where N is equal to or greater than one. The block header includes a hash of the block's transactions, as well as a hash of the prior block's header. In this way, all transactions on the ledger may be sequenced and cryptographically linked together. Accordingly, it is not possible to tamper with the ledger data without breaking the hash links. A hash of a most recently added blockchain block represents every transaction on the chain that has come before it, making it possible to ensure that all peer nodes are in a consistent and trusted state. The chain may be stored on a peer node file system (i.e., local, attached storage, cloud, etc.), efficiently supporting the append-only nature of the blockchain workload.

The current state of the immutable ledger represents the latest values for all keys that are included in the chain transaction log. Because the current state represents the latest key values known to a channel, it is sometimes referred to as a world state. Chaincode invocations execute transactions against the current state data of the ledger. To make these chaincode interactions efficient, the latest values of the keys may be stored in a state database. The state database may be simply an indexed view into the chain's transaction log, it can therefore be regenerated from the chain at any time. The state database may automatically be recovered (or generated if needed) upon peer node startup, and before transactions are accepted.

Some embodiments bring an Agile software development framework to a blockchain for co-authoring software based on the requirements for separate entities that trust each other while requiring transparency and consensus in large scale multi-corporation environments in order to write code together to solve sensitive data problems and ensuring security throughout the software development lifecycle. These embodiments may include advantages such as providing a transparent, immutable source code record system based on fundamental source control system principles and blockchain technology to enable the collaborative real time development of software assets between multiple corporations to reduce the barriers presented by Regulation and Compliance.

Simply stated, some embodiments provide a software development framework based on decentralization. The importance of these embodiments is to provide trusts and an agile development framework in highly regulated areas (e.g., where trust and data integrity are a fundamental roadblock to moving out of waterfall methods of development and co-authoring software in sensitive data industries like Finance, Defense, Aerospace, etc. where multiple vendors are required to build a solution collaboratively).

In some embodiments, branch hash goes into a block. A smart contract may act as a consortium review of new software code introduced into the blockchain. This may create an immutable collaborative source control system.

An agreement from the consortium through smart contract approves the software package for distributed copies among participants to continue iterating together. When consortium review passes, the master ledger is updated and a forced pushed of the new block's hash is updated across developer branches before new changes can be brought for a review.

Some of these embodiments ensure all participants are acting upon the same software while also trusting the data and sources of all software introduced into the development workspace. Master ledger may become the trusted history of the project since inception, and the smart contract runs all security tools, provides a historical trace of downloads, and has signature when a child ledger commit goes up for vote in the smart contract. This allows everyone to have equal viewership and ownership of the solution power from a single software provider or creating a serial chain of exchange that lacks transparency to other vendors.

FIG. 1 illustrates a logic network diagram 100 in a blockchain according to example embodiments. Referring to FIG. 1, the network 100 includes a plurality of company networks 102 ₁ . . . 102 _(N) connect to an enterprise cloud network 104. When a developer joins in any of company networks 102 ₁ . . . 102 _(N), the developer receives a copy 106 _(C1) . . . 106 _(CN) of master ledger 106. The master ledger may include a code and history associated with the master ledger, the code, or both.

In some embodiments, the developer may propose changes to the existing code in the master ledger by modifying copy 106 _(C1) . . . 106 _(CN) of master ledger 106, and in some embodiments, modifying the code within their own firewall. When enterprise cloud network 104 receives a modified copy of the master ledger at branch hash 112, the master ledger is updated. In some embodiments, the master ledger is updated when the required developer smart contract code review standard 108 is met. Blockchain service 110 may detect the updated master ledger and initiate a push of the origin hash to all developer branch 102 ₁ . . . 102 _(N), enforcing synchronization across developer branches before new changes can be proposed.

FIG. 2A illustrates a blockchain architecture configuration 200, according to example embodiments. Referring to FIG. 2A, the blockchain architecture 200 may include certain blockchain elements, for example, a group of blockchain nodes 202. The blockchain nodes 202 may include one or more nodes 204-210. It should be noted that 4 nodes are depicted by way of example only. These nodes participate in a number of activities, such as blockchain transaction addition and validation process (consensus). One or more of the blockchain nodes 204-210 may endorse transactions and may provide an ordering service for all blockchain nodes in the architecture 200. A blockchain node may initiate a blockchain authentication and seek to write to a blockchain immutable ledger stored in blockchain layer 216, a copy of which may also be stored on the underpinning physical infrastructure 214. The blockchain configuration may include one or applications 224 which are linked to application programming interfaces (APIs) 222 to access and execute stored program/application code 220 (e.g., chaincode, smart contracts, etc.) which can be created according to a customized configuration sought by participants and can maintain their own state, control their own assets, and receive external information. This can be deployed as a transaction and installed, via appending to the distributed ledger, on all blockchain nodes 204-210.

The blockchain base or platform 212 may include various layers of blockchain data, services (e.g., cryptographic trust services, virtual execution environment, etc.), and underpinning physical computer infrastructure that may be used to receive and store new transactions and provide access to auditors which are seeking to access data entries. The blockchain layer 216 may expose an interface that provides access to the virtual execution environment necessary to process the program code and engage the physical infrastructure 214. Cryptographic trust services 218 may be used to verify transactions such as asset exchange transactions and keep information private.

The blockchain architecture configuration of FIG. 2A may process and execute program/application code 220 via one or more interfaces exposed, and services provided, by blockchain platform 212. The code 220 may control blockchain assets. For example, the code 220 can store and transfer data, and may be executed by nodes 204-210 in the form of a smart contract and associated chaincode with conditions or other code elements subject to its execution. As a non-limiting example, smart contracts may be created to execute reminders, updates, and/or other notifications subject to the changes, updates, etc. The smart contracts can themselves be used to identify rules associated with authorization and access requirements and usage of the ledger. For example, updated code information 226 may be processed by one or more processing entities (e.g., virtual machines) included in the blockchain layer 216. The result 228 may include information related to the updated master ledger. The physical infrastructure 214 may be utilized to retrieve any of the data or information described herein.

Within chaincode, a smart contract may be created via a high-level application and programming language, and then written to a block in the blockchain. The smart contract may include executable code which is registered, stored, and/or replicated with a blockchain (e.g., distributed network of blockchain peers). A transaction is an execution of the smart contract code which can be performed in response to conditions associated with the smart contract being satisfied. The executing of the smart contract may trigger a trusted modification(s) to a state of a digital blockchain ledger. The modification(s) to the blockchain ledger caused by the smart contract execution may be automatically replicated throughout the distributed network of blockchain peers through one or more consensus protocols.

The smart contract may write data to the blockchain in the format of key-value pairs. Furthermore, the smart contract code can read the values stored in a blockchain and use them in application operations. The smart contract code can write the output of various logic operations into the blockchain. The code may be used to create a temporary data structure in a virtual machine or other computing platform. Data written to the blockchain can be public and/or can be encrypted and maintained as private. The temporary data that is used/generated by the smart contract is held in memory by the supplied execution environment, then deleted once the data needed for the blockchain is identified.

A chaincode may include the code interpretation of a smart contract, with additional features. As described herein, the chaincode may be program code deployed on a computing network, where it is executed and validated by chain validators together during a consensus process. The chaincode receives a hash and retrieves from the blockchain a hash associated with the data template created by use of a previously stored feature extractor. If the hashes of the hash identifier and the hash created from the stored identifier template data match, then the chaincode sends an authorization key to the requested service. The chaincode may write to the blockchain data associated with the cryptographic details. In FIG. 2A, development may commit updates to the development ledger, triggering a review by way of smart contract at 226. One function may be to validate code, and commit updates to master ledger at 228, which may be provided to one or more of the nodes 204-210.

FIG. 2B illustrates an example of a transactional flow 250 between nodes of the blockchain in accordance with an example embodiment. Referring to FIG. 2B, the transaction flow may include a transaction proposal 291 sent by an application client node 260 to an endorsing peer node 281. The endorsing peer 281 may verify the client signature and execute a chaincode function to initiate the transaction. The output may include the chaincode results, a set of key/value versions that were read in the chaincode (read set), and the set of keys/values that were written in chaincode (write set). The proposal response 292 is sent back to the client 260 along with an endorsement signature, if approved. The client 260 assembles the endorsements into a transaction payload 293 and broadcasts it to an ordering service node 284. The ordering service node 284 then delivers ordered transactions as blocks to all peers 281-283 on a channel. Before committal to the blockchain, each peer 281-283 may validate the transaction. For example, the peers may check the endorsement policy to ensure that the correct allotment of the specified peers have signed the results and authenticated the signatures against the transaction payload 293.

Referring again to FIG. 2B, the client node 260 initiates the transaction 291 by constructing and sending a request to the peer node 281, which is an endorser. The client 260 may include an application leveraging a supported software development kit (SDK), such as NODE, JAVA, PYTHON, and the like, which utilizes an available API to generate a transaction proposal. The proposal is a request to invoke a chaincode function so that data can be read and/or written to the ledger (i.e., write new key value pairs for the assets). The SDK may serve as a shim to package the transaction proposal into a properly architected format (e.g., protocol buffer over a remote procedure call (RPC)) and take the client's cryptographic credentials to produce a unique signature for the transaction proposal.

In response, the endorsing peer node 281 may verify (a) that the transaction proposal is well formed, (b) the transaction has not been submitted already in the past (replay-attack protection), (c) the signature is valid, and (d) that the submitter (client 260, in the example) is properly authorized to perform the proposed operation on that channel. The endorsing peer node 281 may take the transaction proposal inputs as arguments to the invoked chaincode function. The chaincode is then executed against a current state database to produce transaction results including a response value, read set, and write set. However, no updates are made to the ledger at this point. In 292, the set of values, along with the endorsing peer node's 281 signature is passed back as a proposal response 292 to the SDK of the client 260 which parses the payload for the application to consume.

In response, the application of the client 260 inspects/verifies the endorsing peers signatures and compares the proposal responses to determine if the proposal response is the same. If the chaincode only queried the ledger, the application would inspect the query response and would typically not submit the transaction to the ordering node service 284. If the client application intends to submit the transaction to the ordering node service 284 to update the ledger, the application determines if the specified endorsement policy has been fulfilled before submitting (i.e., did all peer nodes necessary for the transaction endorse the transaction). Here, the client may include only one of multiple parties to the transaction. In this case, each client may have their own endorsing node, and each endorsing node will need to endorse the transaction. The architecture is such that even if an application selects not to inspect responses or otherwise forwards an unendorsed transaction, the endorsement policy will still be enforced by peers and upheld at the commit validation phase.

After successful inspection, in step 293 the client 260 assembles endorsements into a transaction and broadcasts the transaction proposal and response within a transaction message to the ordering node 284. The transaction may contain the read/write sets, the endorsing peers signatures and a channel ID. The ordering node 284 does not need to inspect the entire content of a transaction in order to perform its operation, instead the ordering node 284 may simply receive transactions from all channels in the network, order them chronologically by channel, and create blocks of transactions per channel.

The blocks of the transaction are delivered from the ordering node 284 to all peer nodes 281-283 on the channel. The transactions 294 within the block are validated to ensure any endorsement policy is fulfilled and to ensure that there have been no changes to ledger state for read set variables since the read set was generated by the transaction execution. Transactions in the block are tagged as being valid or invalid. Furthermore, in step 295 each peer node 281-283 appends the block to the channel's chain, and for each valid transaction the write sets are committed to current state database. An event is emitted, to notify the client application that the transaction (invocation) has been immutably appended to the chain, as well as to notify whether the transaction was validated or invalidated.

FIG. 3 illustrates an example of a permissioned blockchain network 300, which features a distributed, decentralized peer-to-peer architecture, and a certificate authority 318 managing user roles and permissions. In this example, the blockchain user 302 may submit a transaction to the permissioned blockchain network 310. In this example, the transaction can be a deploy, invoke or query, and may be issued through a client-side application leveraging an SDK, directly through a REST API, or the like. Trusted business networks may provide access to regulator systems 314, such as auditors (the Securities and Exchange Commission in a U.S. equities market, for example). Meanwhile, a blockchain network operator system of nodes 308 manage member permissions, such as enrolling the regulator system 310 as an “auditor” and the blockchain user 302 as a “client.” An auditor could be restricted only to querying the ledger whereas a client could be authorized to deploy, invoke, and query certain types of chaincode.

A blockchain developer system 316 writes chaincode and client-side applications. The blockchain developer system 316 can deploy chaincode directly to the network through a REST interface. To include credentials from a traditional data source 330 in chaincode, the developer system 316 could use an out-of-band connection to access the data. In this example, the blockchain user 302 connects to the network through a peer node 312. Before proceeding with any transactions, the peer node 312 retrieves the user's enrollment and transaction certificates from the certificate authority 318. In some cases, blockchain users must possess these digital certificates in order to transact on the permissioned blockchain network 310. Meanwhile, a user attempting to drive chaincode may be required to verify their credentials on the traditional data source 330. To confirm the user's authorization, chaincode can use an out-of-band connection to this data through a traditional processing platform 320.

FIG. 4 illustrates a system messaging diagram 400 for applying blockchain technique for agile software development framework, according to example embodiments. Referring to FIG. 4, the system diagram 400 includes a developer computing device 410, a blockchain system 430, and a network 420 communicating with developer computing device 410 and blockchain system 430. In developer computing device 410 receives at 412 a copy of master ledger from blockchain system 430. At 414, computing device 410 modifies existing code within the copy of the master ledger. Computing system 410 transmits the modified existing code over network 420 to blockchain system 430. At 416, the master ledger is updated, and at 418, a push of the origin hash is initiated to all developer branch 102 ₁ . . . 102 _(N), enforcing synchronization across developer branches before any new changes can be proposed.

FIG. 5A illustrates a flow diagram 500 of an example method of applying blockchain technique for agile software development framework, according to example embodiments. Referring to FIG. 5A, the method 500 may include transmitting at 502 a copy of the master ledger when a developer joins a network. At 504, the method 500 includes receiving proposed changes to the master ledger, and at 506, the method 500 includes updating the master ledger at the branch hash.

FIG. 5B illustrates a flow diagram 500 of an example method of applying blockchain technique for agile software development framework, according to example embodiments. Referring to FIG. 5B, the method 550 may include transmitting a copy of the master ledger, which includes a code and history, at 552. At 554, the method 550 includes receiving one or more changes to the copy of the master ledger, and at 556, updating the master ledger when a required smart contract code standard is met. At 558, the method includes initiating a push of the updated master ledger to one or more developer branches, enforcing synchronization across the one or more developer branches.

FIG. 6A illustrates an example physical infrastructure configured to perform various operations on the blockchain in accordance with one or more of the example methods of operation according to example embodiments. Referring to FIG. 6A, the example configuration 600A includes a physical infrastructure 610 with a blockchain 620 and a smart contract 640, which may execute any of the operational steps 612 included in any of the example embodiments. The steps/operations 612 may include one or more of the steps described or depicted in one or more flow diagrams and/or logic diagrams. The steps may represent output or written information that is written or read from one or more smart contracts 640 and/or blockchains 620 that reside on the physical infrastructure 610 of a computer system configuration. The data can be output from an executed smart contract 640 and/or blockchain 620. The physical infrastructure 610 may include one or more computers, servers, processors, memories, and/or wireless communication devices.

FIG. 6B illustrates an example smart contract configuration among contracting parties and a mediating server configured to enforce the smart contract terms on the blockchain according to example embodiments. Referring to FIG. 6B, the configuration 650B may represent a communication session, an asset transfer session or a process or procedure that is driven by a smart contract 640 which explicitly identifies one or more user devices 652 and/or 656. The execution, operations and results of the smart contract execution may be managed by a server 654. Content of the smart contract 640 may require digital signatures by one or more of the entities 652 and 656 which are parties to the smart contract transaction. The results of the smart contract execution may be written to a blockchain as a blockchain transaction.

The above embodiments may be implemented in hardware, in a computer program executed by a processor, in firmware, or in a combination of the above. A computer program may be embodied on a computer readable medium, such as a storage medium. For example, a computer program may reside in random access memory (“RAM”), flash memory, read-only memory (“ROM”), erasable programmable read-only memory (“EPROM”), electrically erasable programmable read-only memory (“EEPROM”), registers, hard disk, a removable disk, a compact disk read-only memory (“CD-ROM”), or any other form of storage medium known in the art.

An exemplary storage medium may be coupled to the processor such that the processor may read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application specific integrated circuit (“ASIC”). In the alternative, the processor and the storage medium may reside as discrete components. For example, FIG. 7 illustrates an example computer system architecture 700, which may represent or be integrated in any of the above-described components, etc.

FIG. 7 is not intended to suggest any limitation as to the scope of use or functionality of embodiments of the application described herein. Regardless, the computing node 700 is capable of being implemented and/or performing any of the functionality set forth hereinabove.

In computing node 700 there is a computer system/server 702, which is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 702 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.

Computer system/server 702 may be described in the general context of computer system-executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 702 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.

As shown in FIG. 7, computer system/server 702 in cloud computing node 700 is shown in the form of a general-purpose computing device. The components of computer system/server 702 may include, but are not limited to, one or more processors or processing units 704, a system memory 706, and a bus that couples various system components including system memory 706 to processor 704.

The bus represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.

Computer system/server 702 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 702, and it includes both volatile and non-volatile media, removable and non-removable media. System memory 706, in one embodiment, implements the flow diagrams of the other figures. The system memory 706 can include computer system readable media in the form of volatile memory, such as random-access memory (RAM) 710 and/or cache memory 712. Computer system/server 702 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 714 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to the bus by one or more data media interfaces. As will be further depicted and described below, memory 706 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of various embodiments of the application.

Program/utility 716, having a set (at least one) of program modules 718, may be stored in memory 706 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 718 generally carry out the functions and/or methodologies of various embodiments of the application as described herein.

As will be appreciated by one skilled in the art, aspects of the present application may be embodied as a system, method, or computer program product. Accordingly, aspects of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present application may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.

Computer system/server 702 may also communicate with one or more external devices 720 such as a keyboard, a pointing device, a display 722, etc.; one or more devices that enable a user to interact with computer system/server 702; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 702 to communicate with one or more other computing devices. Such communication can occur via I/O interfaces 724. Still yet, computer system/server 702 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 726. As depicted, network adapter 726 communicates with the other components of computer system/server 702 via a bus. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 702. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

Although an exemplary embodiment of at least one of a system, method, and non-transitory computer readable medium has been illustrated in the accompanied drawings and described in the foregoing detailed description, it will be understood that the application is not limited to the embodiments disclosed, but is capable of numerous rearrangements, modifications, and substitutions as set forth and defined by the following claims. For example, the capabilities of the system of the various figures can be performed by one or more of the modules or components described herein or in a distributed architecture and may include a transmitter, receiver or pair of both. For example, all or part of the functionality performed by the individual modules, may be performed by one or more of these modules. Further, the functionality described herein may be performed at various times and in relation to various events, internal or external to the modules or components. Also, the information sent between various modules can be sent between the modules via at least one of: a data network, the Internet, a voice network, an Internet Protocol network, a wireless device, a wired device and/or via plurality of protocols. Also, the messages sent or received by any of the modules may be sent or received directly and/or via one or more of the other modules.

One skilled in the art will appreciate that a “system” could be embodied as a personal computer, a server, a console, a personal digital assistant (PDA), a cell phone, a tablet computing device, a smartphone or any other suitable computing device, or combination of devices. Presenting the above-described functions as being performed by a “system” is not intended to limit the scope of the present application in any way but is intended to provide one example of many embodiments. Indeed, methods, systems and apparatuses disclosed herein may be implemented in localized and distributed forms consistent with computing technology.

It should be noted that some of the system features described in this specification have been presented as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, graphics processing units, or the like.

A module may also be at least partially implemented in software for execution by various types of processors. An identified unit of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions that may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module. Further, modules may be stored on a computer-readable medium, which may be, for instance, a hard disk drive, flash device, random access memory (RAM), tape, or any other such medium used to store data.

Indeed, a module of executable code could be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.

It will be readily understood that the components of the application, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the detailed description of the embodiments is not intended to limit the scope of the application as claimed but is merely representative of selected embodiments of the application.

One having ordinary skill in the art will readily understand that the above may be practiced with steps in a different order, and/or with hardware elements in configurations that are different than those which are disclosed. Therefore, although the application has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent.

While preferred embodiments of the present application have been described, it is to be understood that the embodiments described are illustrative only and the scope of the application is to be defined solely by the appended claims when considered with a full range of equivalents and modifications (e.g., protocols, hardware devices, software platforms etc.) thereto. 

1. A method, comprising: transmitting a copy of the master ledger when a developer joins a network; receiving proposed changes to the master ledger; and when a consortium review of the proposed changes passes, updating (i) the master ledger at the branch hash and (ii) a forced push of a new block's hash across branches, wherein the updating the forced push occurs before a consortium review of any additional proposed changes occurs, wherein the forced push is a forced sync.
 2. The method of claim 1, wherein the copy comprises a code and history associated with the master ledger.
 3. The method of claim 1, wherein the receiving of the proposed changes comprises receiving a modified copy of the master ledger, the modifications performed within a firewall of the network for the developer.
 4. The method of claim 1, wherein the updating of the master ledger comprises updating the master ledger when a required developer smart contract code review standard is met.
 5. The method of claim 1, further comprising: upon updating of the master ledger, initiating a push sequence of the original hash to all developer branch hash to enforce synchronization across the developer branch before any further changes are proposed.
 6. The method of claim 1, wherein the master ledger is a trusted history of a project.
 7. The method of claim 1, wherein a smart contract provides a historical trace of downloads and includes a signature when a child ledger commit goes upon for vote in the smart.
 8. A system, comprising: a server comprising at least one processor and memory comprising a set of instructions, wherein the at least one processor and the set of instructions cause the server to: transmit a copy of the master ledger when a developer joins a network; receive proposed changes to the master ledger; and when a consortium review of the proposed changes passes, update (i) the master ledger at the branch hash and (ii) a forced push of a new block's hash across branches, wherein the updating the forced push occurs before a consortium review of any additional proposed changes occurs, wherein the forced push is a forced sync.
 9. The system of claim 8, wherein the copy comprises a code and history associated with the master ledger.
 10. The system of claim 8, wherein the at least one processor and the set of instructions cause the server to receive the modified copy of the code, the modifications to the modified copy are performed within a firewall of the network for the developer.
 11. The system of claim 8, wherein the at least one processor and the set of instructions cause the server to update the master ledger when a required developer smart contract code review standard is met.
 12. The system of claim 8, wherein the at least one processor and the set of instructions cause the server to, upon update of the master ledger, initiate a push sequence of the original hash to all developer branch hash to enforce synchronization across the developer branch before any further changes are proposed.
 13. The system of claim 8, wherein the master ledger is a trusted history of a project.
 14. The system of claim 8, wherein a smart contract provides a historical trace of downloads and includes a signature when a child ledger commit goes upon for vote in the smart.
 15. A non-transitory computer readable medium comprising instructions, that when read by a processor, cause the processor to perform: transmit a copy of the master ledger when a developer joins a network; receive proposed changes to the master ledger; and when a consortium review of the proposed changes passes, update (i) the master ledger at the branch hash and (ii) a forced push of a new block's hash across branches, wherein the updating the forced push occurs before a consortium review of any additional proposed changes occurs, wherein the forced push is a forced sync.
 16. The non-transitory computer readable medium of claim 15, wherein the copy comprises a code and history associated with the master ledger.
 17. The non-transitory computer readable medium of claim 15, wherein the processor is further configured to receive a modified copy of the master ledger, the modifications performed within a firewall of the network for the developer.
 18. The non-transitory computer readable medium of claim 15, wherein the processor is further configured to update the master ledger when a required developer smart contract code review standard is met.
 19. The non-transitory computer readable medium of claim 15, wherein the processor is further configured to initiate a push sequence of the original hash to all developer branch hash to enforce synchronization across the developer branch before any further changes are proposed.
 20. The non-transitory computer readable medium of claim 15, wherein the master ledger is a trusted history of a project. 